Assertionless Test ^^^^^ **Definition:** * A test that does not contain at least one valid assertion is not a real test as it does only execute plain source-code, but never assert any data, state or functionality. * Pretending to assert data and functionality, but does not **Also Known As:** * Lying Test, The Line Hitter, No Assertions **Code Example:** .. code-block:: Smalltalk // Smalltalk ICCreateCalendar>>TesttestCreatingSeveralCalendars self addCalendarWithName: ’new Calendar 1’. self addCalendarWithName: ’new Calendar 2’. self addCalendarWithName: ’new Calendar 3’. self addCalendarWithName: ’new Calendar 1’. self addCalendarWithName: ’new Calendar 2’. self addCalendarWithName: ’new Calendar 3’. **References:** .. admonition:: Quality attributes * :octicon:`file-code;1em` - Code Example * :octicon:`comment-discussion;1em` - Cause and Effect * :octicon:`graph;1em` - Frequency * :octicon:`sync;1em` - Refactoring * `Assessing test quality ‐ TestLint `_ :octicon:`file-code;1em` :octicon:`comment-discussion;1em` * `Rule-based Assessment of Test Quality `_ :octicon:`file-code;1em` :octicon:`graph;1em` :octicon:`sync;1em` * `Test Smell Detection Tools: A Systematic Mapping Study `_ * `Test Smell Detection Tools: A Systematic Mapping Study `_ * `TestQ: Exploring Structural and Maintenance Characteristics of Unit Test Suites `_ * `What We Know About Smells in Software Test Code `_